# gcc(1) completion
#
# The only unusual feature is that we don't parse "gcc --help -v" output
# directly, because that would include the options of all the other backend
# tools (linker, assembler, preprocessor, etc) without any indication that
# you cannot feed such options to the gcc driver directly.  (For example, the
# linker takes a -z option, but you must type -Wl,-z for gcc.)  Instead, we
# ask the driver ("g++") for the name of the compiler ("cc1"), and parse the
# --help output of the compiler.


comp_include _expand _filedir _get_cword


_gcc()
{
    local cur cc backend

    COMPREPLY=()
    cur=`_get_cword`

    _expand || return 0

    case "$1" in
    gcj)
        backend=jc1
        ;;
    gpc)
        backend=gpc1
        ;;
    *77)
        backend=f771
        ;;
    *)
        backend=cc1 # (near-)universal backend
        ;;
    esac

    if [[ "$cur" == -* ]]; then
        cc=$( $1 -print-prog-name=$backend )
        # sink stderr:
        # for C/C++/ObjectiveC it's useless
        # for FORTRAN/Java it's an error
        COMPREPLY=( $( $cc --help 2>/dev/null | tr '\t' ' ' | \
                   sed -e '/^  *-/!d' -e 's/ *-\([^ ]*\).*/-\1/' | \
                   command grep "^$cur" | sort -u ) )
    else
        _filedir
    fi
} # _gcc()


